Refine Your Search

Topic

Author

Search Results

Standard

Vertical Dynamic Balancing Systems – Isolating Repeatability Issues in Challenging Applications

2021-05-26
WIP
ARP8911
This new Aerospace Recommended Practice will serve as a practical resource that offers guidance to both the machine operator and Process Engineer for isolating the source(s) of non-repeatability in measured unbalance data. The content of this standard addresses: • Vertical Dynamic Machine Capability to achieve the specified unbalance tolerances and repeat within those tolerances • Tooling Capability to repeat within the specified unbalance tolerances • Rotor characteristics that may preclude repeating within the required unbalance tolerances.
Standard

Vehicle OBD II Compliance Test Cases for J1979-2

2019-08-23
WIP
J1699-5
The main purpose is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979-2: E/E Diagnostic Test Modes
Standard

Vehicle OBD II Compliance Test Cases

2021-04-28
CURRENT
J1699/3_202104
The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534-2 feature “Mixed Format Frames on a CAN Network.”
Standard

Vehicle OBD II Compliance Test Cases

2021-05-04
WIP
J1699/3
The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534 2 feature “Mixed Format Frames on a CAN Network.”
X